home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Overload Trio 2
/
Shareware Overload Trio Volume 2 (Chestnut CD-ROM).ISO
/
dir30
/
w12bug2.zip
/
W12BUG.TXT
Wrap
Text File
|
1994-04-24
|
40KB
|
833 lines
W12BUG.TXT - ACAD Windows R12c1 bug list
Compiled by Mike Dickason Compuserve[72711,3404]
December 7, 1993 Initial posting Bugs 1-74
April 24, 1994 Second posting Updated for R12c3
This will be the last posting of this file. Bugs in R12c3
Windows will be available on the ACAD forum as 12C3W.ZIP.
The following list of ACAD Windows R12 bugs and corresponding
work arounds was compiled from a combination of problems I have
personally encountered and from messages posted on the ACAD forum
of Compuserve. I am not an employee of AutoDesk, nor did I
compile this list to discredit AutoDesk. Indeed, I am quite
happy with R12, but as with any program of this size and
magnitude, there are some bugs.
This is not an official nor a complete list of Windows R12 bugs.
It is meant to be used as an informative list to help other users
who might be encountering similar problems. All of the problems
on this list have been reported to and acknowledged by ADESK. If
you know of any bugs which are not included on this list, I would
be interested in hearing about them, solely for the purpose of
keeping the list up to date. Unless noted otherwise, the bugs
are present in the North American version of ACAD R12c1c for
Windows.
Finally, this list is not presented in any order of importance.
Several of the nastier bugs are actually listed towards the end
of the file.
The following bugs were addressed in R12c3: 1, 2, 5-8, 10, 11,
13, 15-18, 20-24, 26, 28-33, 36-38, 40-42, 45-50, 53-56, 58-62,
66, 67, 69, 70, 72, 74.
*1. If you perform a PEDIT Join command on a polyline containing
curve information, the resultant joined polyline is stripped
of all the curve information leaving you with a polyline
made entirely of straight line segments. The workaround is
to explode the polyline containing the curve information,
then use the PEDIT Join command to tie everything back
together in a new polyline. Technically, this is not a bug
since it is documented in the AutoCAD Reference Manual.
*2. With a closed polyline, if you perform the sequence PEDIT,
Edit vertex, Break, the command will not only break out the
segment between the specified vertices, but it also removes
the "closing" segment of the polyline leaving you with two
separate polylines if you attempt to break out an interior
section. No known workaround. Note: This problem occurred
in earlier versions of ACAD and is not unique to R12. Fixed
in R12c3.
3. When using the new Shift to Add feature for building
selection sets, the "Window" and "Crossing" selection
options add to the current selection set instead of
replacing it as documented. No known work around.
4. If you perform a Dview Twist on a drawing, then plot with a
window, the coordinates of the window corners displayed in
the new plot dialog box do not match the actual coordinates
that were picked. Regardless of what the plot window shows,
the actual coordinates picked are used for generating the
plot. This appears to related to the variable "TARGET",
which changes after a DVIEW, but never seems to be set back
to its default value (i.e. start a new drawing, look at the
value of TARGET, then do a Dview Twist 300, Dview Twist 0,
and then look at TARGET again and it is different). No
known work around.
*5. R12 has a problem with Wblocks and file locking when using
relative paths to specify the drawing name. With file
locking turned on, if I open a file with a relative path,
then attempt to Wblock the drawing back to itself using the
same relative path, ACAD reports the following error
message:
Unable to lock file .\MIKE
File write locked by USER1
at 10:00 on 08/13/1992
The command sequence to show this...
Command: OPEN
File name: .\MIKE
Command: WBLOCK
File name: .\MIKE
R11 didn't exhibit this problem. The only way to make it
work in R12 is to type out the full path for the Wblock
name, which is a pain when you have long paths for the file
directories.
The same problem occurs if you open a new drawing with a
relative path then attempt to save it using the SAVE
command. Fixed in R12c3.
*6. There is a bug in the implementation of the alternate-font-
prompt-reduction (AFPR) mechanism. AFPR is a new feature in
R12 which is supposed to cut down on the number of prompts
for "Can't find font 'XXX'" when you open a drawing by
substituting the font you specify for the first missing font
for each remaining style in the drawing which uses the same
font. Turns out that AFPR is case-sensitive, so if the
first font was really entered as "helv", then it won't match
the next one if it was entered as "HELV". No known
workaround. Fixed in R12c3.
*7. The new variable PICKAUTO does not work. Regardless of its
setting, ACAD allows you to draw a selection window (both
window and crossing window) automatically at the "Select
objects: " prompt. Setting PICKAUTO to 0 is supposed to
disable this automatic windowing, but it doesn't. Fixed in
R12c3.
*8. There's a bug in the POSTSCRIPT sampleprolog. If you
included the code-handling for linetypes, there's a line
that refers to "acad-ltype-known", and another that refers
to "acad-linetype-known". They should both be the same; if
not, your printout will probably fail silently. In
acad.psf, globally change acad-ltype-known to acad-linetype-
known. Fixed in R12c3.
9. After restoring a PCP file which has a default plot file
name which contains a path, any PCP files saved (during the
same editing session) will contain the default plot file
name with path that was originally read in, instead of the
current default plot file name.
*10. When saving a PCP file, if the current time is less than 10
minutes past the hour, the leading 0 of the minutes in the
time field of the PCP is dropped, i.e. 3:05pm is written as
15:5 instead of 15:05. Fixed in R12c3.
*11. In LISP, passing a "nil" instead of a 2D point to the
new_dialog command generates a causes ACAD to stop
responding to all input. The following code demonstrates the
problem:
(setq di_dcl_id (load_dialog "dlgtest.dcl"))
(new_dialog "dimensions" di_dcl_id "" nil)
Fixed in R12c3.
*12. The DDCHPROPS command will not allow you to change an entity
to a locked layer while both the CHANGE and CHPROP commands
will. Fixed in R12c3.
*13. The lisp expression (ssget "X" (list (cons 0 "INSERT") (cons
-4 "=,=,=") (cons 10 (list 0 0 z)))) doesn't work. The z
coordinate isn't being evaluated in the relational test with
blocks. Fixed in R12c3.
14. Create a visible attribute on layer 0. Create a block
called TEST which consists solely of the attribute you just
defined. Make a new layer called HOWCOME and insert the
TEST block onto this layer and enter "THIS IS TEXT" at the
attribute value prompt. Freeze layer 0. The attribute
value of "THIS IS TEXT" is still visible on the screen, as
it should be since anything created on Layer 0 is supposed
to take on the properties of the insertion layer. Now try
to select the block using any command, including DDATTE,
ERASE, MOVE, COPY, etc. and you will not be able to. The
only known workaround is to THAW Layer 0.
*15. When plotting from Paperspace, filled entities (i.e. arrow
heads, fat polylines, solids, etc.) contained within an XREF
but are on a layer which is frozen using VPLAYER show up in
the plot preview and also in the actual plot. The following
script demonstrates the problem.
layer
m
solids
solid
5,5
10,5
7,10
saveas
DWG1
new
DWG2=
xref
attach
DWG1
0,0
tilemode
0
mview
0,0
15,15
zoom
ext
vplayer
freeze
solid*
All
At this point, if you do a full plot preview, the solid is
displayed even though the layer has been frozen. The only
workaround is to freeze the layer in the original drawing
instead of using VPLAYER in the drawing which contains the
XREF. Fixed in R12c3.
*16. Attempting to use entmake or ads_entmake to generate a
polyline in R12 which uses the new continuous linetype
pattern will not generate any entites in the drawing. The
following lisp routine demonstrates the problem.
(defun c:no_ent ()
(setvar "PLINEGEN" 1)
(entmake '( (0 . "POLYLINE")
(62 . 5)
(6 . "DASHED")
(66 . 1)
(70 . 128) ; <<<<---- change this to (70 . 0)
; and it works but the
; continuous linetype
; is not displayed
)
)
(entmake '( (0 . "VERTEX")
(10 1.0 1.0 0.0)
(6 . "DASHED")
(66 . 1)
)
)
(entmake '( (0 . "VERTEX")
(10 5.0 1.0 0.0)
(6 . "DASHED")
(66 . 1)
)
)
(entmake '( (0 . "VERTEX")
(10 10.0 5.0 0.0)
(6 . "DASHED")
(66 . 1)
)
)
(entmake '((0 . "SEQEND")))
)
Fixed in R12c3.
*17. When plotting to a color Postcript device (PLOT, not PSOUT),
the plot file does not correctly handle color changes when
going from a filled entity with a color to a non-filled
entity which has its color set to BYLAYER. For example,
whenever a filled polyline is encountered, subsequent lines,
text, etc. are plotted in the last filled polyline's color
rather than in their specified color. The work around is to
do a chprop and set every entity to its desired color
instead of leaving color set bylayer. Fixed in R12c3.
*18. When using the fillet command on lines that are residing on
different layers, the fillet arc will be created on the
current layer with the current layer color and current layer
linetype rather than on the current layer in the color
currently set by the color command and the current linetype
set by the linetype command. No known workaround. Same
problem applies to the CHAMFER command. Fixed in R12c3.
19. ACAD has a highlighting bug relating to the new 31 bit
display mode of R12. When you zoom in to a very small
portion of the drawing and do a regen, then zoom out to
display a much larger area without forcing a regen, any
items which are then selected at a "Select objects" prompt
don't appear to be highlighted. This wasn't a problem
before release 12 because you could never zoom back out far
enough after the first regen without forcing a second regen,
but it is now possible with the 31 bit display. The only
workaround is to do a second regen with the larger portion
of the drawing displayed.
*20. With FILEDIA=1, if you have a repeating menu command such as
[Fan]*^c^cinsert c:/acad/elecsyms/fan which attempts to
insert a non-existant block, the ACAD alert box pops up
stating that the block can't be found. When you click on
the OK button, the box instantly reappears because the
command is being repeated. The work around is to click on
the OK button and then instantly hit the ^C button. It
might take several tries, but ACAD will eventually stop
running the command and return you to the command prompt.
Fixed in R12c3.
*21. ACAD does not allow the valid DOS filename characters
"`~!@#$%^&{}()'" to be used with the NEW, SAVE, WBLOCK, and
SAVEAS commands. Interestingly enough, the commands OPEN
and INSERT do allow these characters to be used. Because of
this discrepancy, it is possible to open an existing drawing
which contains these characters but you won't be able to
save it back to the disk with changing its name.
Technically, this is not a bug since it is documented in the
AutoCAD Reference Manual.
*22. Having Limit Checking turned on prevents the you from
configuring your tablet menu. Attempting to configure the
tablet menu with Limit Checking on results in the message
"Outside Limits" being display for each corner of the menu.
The work around is to turn it off with the command, LIMITS
OFF. Fixed in R12c3.
*23. With file locking enabled, start a new drawing and attempt
to DXFIN a .DXF file which contains errors. ACAD will
generate an error message about the invalid DXF file, then
re-initialize the drawing editor so that the current drawing
name is "UNNAMED" but it leaves the .DWK file for the
original new drawing. You then have to delete the original
.DWK before you can attempt to start a new drawing with the
same name. Partially fixed in R12c3. The .DWK is now
removed, but the drawing name is still changed back to
UNNAMED.
*24. The command DDIM does not work transparently, even though it
is documented to do so. The only workaround is to run the
command from the "Command:" prompt. Documentation bug.
This command was not intended to run transparently.
25. When performing a Zoom Extents within a viewport in
Paperspace, ACAD is incorrectly computing the drawing
extents based on every entity in the drawing instead of only
those thawed in the current viewport. To show this, start a
new drawing, then place a circle at (5,5) with a 10' radius
on LAYER1, then create a second circle at (1000,1000) with a
10' radius on LAYER2. Set TILEMODE=0 and create then use
MVIEW to create 2 viewports. Run VPLAYER and freeze LAYER1
in one viewport and LAYER2 in the other viewport. Now
perform a Zoom Extents in each viewport. ACAD is zooming
over the entire model space instead of just the object
space. No known workaround.
*26. Using GRIP editing on 2D polyline vertices, ACAD allows you
to change the vertex elevation by osnaping to a point in the
drawing with an elevation different than the vertex. When
you do this, ACAD updates the polyline header and the vertex
you are editing to reflect the new elevation, but it doesn't
change any of the other vertices within the polyline. If
you perform an AUDIT after doing this grip editing, ACAD
reports errors with a non-planar 2D polyline. Fixed in
R12c3.
27. The new TRIM with Fence option does not work correctly with
polylines which cross the trimming boundary more than twice.
The only workaround is to keep repeating the trim command
until all of the polyline is gone.
*28. There is "lockup" problem with a combination of DVIEW,
LTSCALE, DRAGMODE, and INSERT using a block containing
entities with non-continuous linetypes. The following lisp
routine demonstrates the lockup:
(defun c:lock ()
(setvar "dragmode" 2)
(command "._zoom" "w" (list 1999995 499995) (list 2000105
500100))
(command "._line" (list 2000000 500000) "@100,0" "")
(command "._chprop" (entlast) "" "lt" "hidden2" "")
(command "._block" "lock" (list 0 0) (entlast) "")
(command "._dview" "" "")
(command "._ltscale" 50)
(command "._insert" "lock" (list 0 0))
)
Start a new drawing with no prototype, run the lisp routine
and ACAD will lock up the system. If I remove the call to
Dview, leave the line's linetype as continuous, leave
LTSCALE=1, or turn of DRAGMODE, the lockup problem
disappears. Even though it appears to do so, this does not
really lockup ACAD. If you allow ACAD to continue to run
(sometimes for several hours), the next prompt in the Insert
command will eventually appear. At this point you can ^C
out of the routine and save your drawing. Fixed in R12c3.
*29. Drawing created with R11 which contain XREF's and have
VISRETAIN=1 aren't handled properly by R12. When these
drawings are opened in R12, all of the layers contained
within the XREF's have their linetypes changed to
continuous, regardless of how they were set in R11. The
only workaround is to open the drawing with R11 and set
VISRETAIN=0 before attempting to open the drawing with R12.
*30. The command DDMODIFY overwrites the AutoLisp command (ver).
This occurs because there are several places in DDMODIFY.LSP
where the program does a (setq ver ...), which effectively
reassigns the symbol ver from a subroutine to a variable.
Fixed in R12c3.
*31. R12 doesn't correctly display or plot certain circles with
non-continuous linetypes contained within a block. The
following lisp routine demonstrates the problem.
(defun c:showme ()
(setvar "ltscale" 1)
(command "._layer" "make" "hidden" "lt" "hidden""""")
(command "._circle" (list 0 0) (/ 3.0 32.0))
(command "._block" "no_show" (list 0 0) (entlast) "")
(setvar "ltscale" 48)
(command "._insert" "no_show" (list 0 0) 48 "" "")
(command "._zoom" "e")
)
If the block is exploded at this point, the circle will show
up with a hidden linetype. To make the circle display
correctly without exploding the block, the LTSCALE must be
set to a value less than PI/2 (1.5706 works). Fixed in
R12c3.
*32. The lisp expression (ssget "X" (list (cons 0 "ARC") (cons -4
"=,=,=") (cons 10 (list 0 0 z)))) doesn't work. The z
coordinate isn't being evaluated in the relational test with
arcs. Fixed in R12c3.
*33. With HIGHLIGHT=0, using "U" to undo the previous selection
while in the "Select objects: " prompt acts like
HIGHLIGHT=1. To show this, load a drawing with 5000+
entities, do a LIST, and at the "Select objects:" prompt
type ALL. ACAD reports XXXX entities selected. Now type
"U". Instead of instantly reporting that XXXX entities were
removed, it takes several seconds for the message to appear.
Now if you type ALL again, ACAD takes much longer than the
original time to report XXXX entities selected. No known
workaround. Fixed in R12c3.
34. If you use WBLOCK <dwgname> * to purge a drawing, and the
drawing contains xrefs, Release 12 resets all xref layer
visibility, color, and linetype settings to the values in
the external drawings, even when you've changed some of
these values and set VISRETAIN to 1 to keep the changes.
Workaround: Use the PURGE command instead of WBLOCK * (note
that, because of block nesting, you sometimes have to go
through several OPEN and PURGE cycles in order to purge
everything). Alternately, if your changes to xref layers
are minimal, simply reapply them after purging with WBLOCK
*.
35. If you create a custom linetype that consists of a repeated
sequence of two or more dots, AutoCAD doesn't display or
plot the linetype correctly. For instance, suppose you
create a "3-dot" linetype (a sequence of 3 closely spaced
dots, followed by a wide space, followed by 3 more dots...)
by adding the following linetype definition to ACAD.LIN:
*3DOTS,... ... ... ... ...
A,0,-.25,0,-.25,0,-.5
When you draw random line segments with this linetype, some
of the segments are continuous, and in other segments the
dot groupings are incorrectly spaced or contain the wrong
number of dots. Note that this bug isn't new with Release
12.
Workaround: Although we haven't discovered a completely
effective workaround, drawing polylines with linetype
generation turned on minimizes the problem. The first and
last sequences of dots are still wrong, but the remaining
dots are fine and the continuous segments disappear. To
turn on linetype generation, set the Release 12 system
variable PLINEGEN to 1 before drawing the polylines. Use
the PLUD command or the Ltype gen option of the PEDIT
command to change existing polylines.
*36. The AutoLISP statement (getvar "LIMCHECK") triggers Release
12's DBMOD ("drawing database has been modified") system
variable. As a result, when you next use OPEN, NEW, or
QUIT, AutoCAD reports that "the current drawing has been
modified" and asks whether you want to save changes, even if
you haven't changed anything. This problem can confuse
users who have come to rely on Release 12 to prompt them
only when they really have made changes.
Workaround: Avoid using (getvar "LIMCHECK") in ACAD.LSP,
since it will cause AutoCAD to prompt you to save changes
with every drawing (as Release 11 and prior versions did).
Fixed in R12c3.
*37. When running the Insert command, at the "Block name" prompt
if you use the tilde key (~) to invoke the file dialog box
to select the block for insertion, ACAD changes the current
drawing name to that of the inserted block. The Undo
command will not undo this change. Fixed with the C1C
update. Fixed in R12c3.
*38. The COPYCLIP command does not work if the variable HIGHLIGHT
is set to 0. Set HIGHLIGHT=1 before running this command.
Fixed in R12c3.
39. The COPYCLIP command clears out the previous selection set
currently established in the drawing. There is no known
workaround.
*40. If you hit the F1 key for context sensitive help in the
pull-down menus, you will sometimes get the message "Help
topic does not exist". To fix this problem, download the
file FIXHLP.ZIP from the ACAD forum on CIS. Fixed with the
C1C update. Fixed in R12c3.
*41. The DLINE.LSP command that ships with ACAD R12WIN does not
work when used to draw an arc. To fix the problem, edit
DLINE.LSP in the support directory and change all
occurrences of _pause to pause, or copy the DLINE.LSP that
ships with R12 for DOS. Also fixed with the C1C update.
Fixed in R12c3.
*42. When configured for the Summasketch series of digitizers,
occasionally, you will be unable to close a dialog box. For
example, when you choose File/Preferences from the menu, the
Preferences dialog box is displayed. When the problem
occurs, you are not able to CLOSE the dialog box; choosing
Cancel or OK will eliminate the box temporarily, but the box
will reappear within seconds (milli-seconds). There is a
problem with the DGSYS driver supplied with ACAD. Fixed
with the C1C update. Fixed in R12c3.
43. Call up the DDMODIFY dialog box then select the CANCEL
button. Type "U" to undo the last command and ACAD will
report "Start of Group encountered. Must enter UNDO END to
go back further.". To fix the problem, edit DDMODIFY.LSP
and add the line "(ai_undo_pop)" after line 128 which
currently reads "(defun reset ()".
44. With TILEMODE=1, thaw a layer containing entities in both
Model and Paper Space. Set TILEMODE=0. Entities on the
thawed layer residing in paperspace do not display, but they
will plot. To see these entities, you must freeze then thaw
the layer.
*45. With REGENMODE=0, freeze a layer, do a REGEN, then thaw the
layer you just froze and AutoCAD will report "Regen queued".
At this point insert any block into the drawing at any
location and take the defaults for scale and rotation
factors. Now do a REGEN to take care of the "Regen queued"
from the thaw operation above. The frozen/thawed layer will
not appear on the screen, but it will plot. To get the
layer to appear on the screen, you need to freeze and thaw
any layer in the drawing. Fixed in R12c3.
*46. When you are plotting using metric units and you save the
pen settings out to a .PCP file, all of the pen weights are
divided by 25.4 as they are written to the file. For
example, if you set Pen 1 to have a width of 0.254, then
save the pen settings to \TEST.PCP, when you view TEST.PCP
Pen 1 will have a width of 0.01 instead of 0.254. The only
known workaround is to edit the .PCP file to enter the
correct values.
*47. With FILEDIA=1, if you run the FILES command, select the
"Unlock file..." button, keep the default filespec of *.*
and select the "Select all" button, and then the "OK"
button, a dialog box will sometimes appear listing one of
the selected file names with a message stating that "This
file is already in use. Use a new filename or close the
file in use by another application". At this point all you
can do is cancel out of the routine. The workaround is to
set FILEDIA=0 and run the command without the dialog boxes.
Fixed in R12c3.
*48. With FILEDIA=1, if you run the FILES command, select the
"Copy file..." button, then specify a .DXF file as the
source file you will not be prompted for the destination
file. When you Exit out of the FILES dialog, the file is
not copied, but instead ACAD will run the DXFIN command and
attempt to DXFIN the file you specified as the source file
for the file copy. The workaround is to set FILEDIA=0 and
run the command without the dialog boxes, or to use the
Windows file manager to copy the file. Fixed in R12c3.
*49. With FILEDIA=1, if you run the FILES command, select the
"Rename file..." button, then specify a .DXF file as the old
file name, you will not be prompted for the new file name.
When you Exit out of the FILES dialog, the file is not
renamed, but instead ACAD will run the DXFIN command and
attempt to DXFIN the file you specified as the old file name
for the file rename. The workaround is to set FILEDIA=0 and
run the command without the dialog boxes, or to use the
Windows file manager to rename the file. Fixed in R12c3.
*50. With FILEDIA=1, if you run the FILES command, select the
"Delete file..." button, then specify a .DXF file as the old
file name, the file will not be deleted. Instead, when you
Exit out of the FILES dialog, ACAD will run the DXFIN
command and attempt to DXFIN the file you specified as the
file to be deleted. The workaround is to set FILEDIA=0 and
run the command without the dialog boxes, or to use the
Windows file manger to delete the file. Fixed in R12c3.
51. The lisp function (getfiled) and the ADS function
ads_getfiled() both have a problem if the passed file
extension is null. To demonstrate the problem at the
command prompt run (getfiled) with the following arguments:
(getfiled "Output name" "\\ACADWIN\\SUPPORT" "" 1)
or
(getfiled "Output name" "\\ACADWIN\\SUPPORT" "*" 1)
With either case, if the user enters a filename but does not
specify an extension, i.e. the user types in ERASEME for
the filename, one of two things happens.
1) If the file already exists, you get an alert box
stating that the file already exists and prompts if it
should be overwritten. This is normal and expected.
2) If the file name does not exist, you get an error box
stating that the file "ERASEME.*" is an invalid
filename. To get around the problem, the user is
forced to type in "ERASEME." to get a filename with no
extension.
The same problem occurs when activated through
ads_getfiled().
*52. When running Windows in 640x480 mode, start ACAD. Run the
MENU command and double click on the ACAD.MNU file. Run the
MENU command a second time and double click on the SHAFT.MNU
file. Finally, run the MENU command one more time. The
file search pattern has changed from *.MNU to *.LIN. Once
you reset the search pattern to *.MNU, it will not reset to
*.LIN until the next time you start ACAD. Fixed in R12c3.
*53. The following sequence changes the default filespec pattern
in the STYLE dialog box from "*.SHX, *.PFB" to "*.PLT".
First, start an unnamed drawing, then type STYLE, choose the
default STANDARD, use TXT.SHX, set the size to .1 and take
the rest of the defaults. Next, type STYLE, define a new
style called TEST, use ROMAND.SHX, set the height to .2 and
take the rest of the defaults. Now, type STYLE again, and
the dialogue box comes up with a default file extension of
.PLT instead of .SHX,.PFB. At this point,if you change the
default filespec back to .SHX,.PFB, it will not change back
to .PLT until the next time you start ACAD. Fixed in R12c3.
*54. The style dialog box requires you to type in the font
extension if you type in the font name instead of picking it
from the list. To show this, start an unnamed drawing, then
type STYLE, choose the default STANDARD. The STYLE dialog
box comes up, with TXT as the default font name. If you hit
<Enter> to accept this, an error box appears stating that it
can't find the file "txt.pfb". For some reason, it appears
that ACAD is defaulting to a .PFB extension for the fonts
instead of the typical .SHX extension. The workaround is to
physcially pick the TXT.SHX font from the displayed list.
Fixed in R12c3.
*55. With the plotter set up for metric units, when you save a
plot configuration file, all the pen widths written to the
file are divided by 25.4. The only workaround is to edit
the .PCP file and do a search and replace of the .010
numbers in your .PCP file to .254.
*56. When using Autocad for Windows with Windows for Workgroups,
if you have your temporary files redirected to a local drive
and directory instead of DRAWING and use the End command to
exit ACAD, your drawing will become corrupted. This appears
to actually be a WFW bug. The workaround is to go through
config and set this back to DRAWING, or to use the SAVE,
WBLOCK, or QSAVE commands instead of the END command. This
is now documented in the README.DOC file with R12c3.
57. The POP0 menu will appear at the location of the mouse
cursor instead of the crosshair location when using Wintab
drivers. No known workaround.
*58. ACAD R12Win is unable to evaluate the following DIESEL
expression.
[]$M=$(if,$(=,$(getvar,PLATFORM),"386DOSExtender"),
'redraw,'redraw)
No known workaround. It turns out this is not a bug. The
$(eq, ... ) function, not the $(=, ... ) should be used to
compare two strings. $(=, ... ) is for numbers only.
*59. There is a bug in freeplotting that causes it to hide lines
automatically. Since hiding has the side effect of causing
solid fills to not show up. The only workaround is to not
use freeplot. Fixed in R12c3.
*60. When attempting to use two sessions of AutoCAD for Windows
R12 will generate the error message
FATAL ERROR: The file "C:\ACADWIN\acad.pwd" is corrupted.
This is a result of having crashed out of AutoCAD at some
time. Check the file ACADNODE.INI in the windows directory,
and make sure that DirtyCount is set to zero when no AutoCAD
sessions are running. If it is set to 1 with no sessions
running you will get this problem when exiting from a second
session. Fixed in R12c3.
*61. The ***BUTTONS2, 3, 4 sections are broken in R12Win. This
means that the shift, ctrl, and ctrl-shift keys will not
work. No known workaround. Fixed in R12c3.
*62. The (menucmd) function will not work correctly on pop menus
numbered 1,2, or greater than 9. No known workarounds.
*63. ACAD will not read in a .PCP file when using a script to
plot. The only workaround is to plot out all plots to the
same printer at once and then manually change the PCP file
and then script out more plots using the updated settings.
Fixed in r12c3.
64. Trying to redefine the right button on a puck (button 3) as
an alternate pick button, using a backslash will not work.
Using backslash in R12Win menus doesn't work. Status in
R12c3 unknown.
65. The layer indicator window in the ACADWIN toolbar does not
always agree with the actual layer even though the color is
correct and the current layer in the layer dialog box is
correct. This occurs in the situation where the difference
in layer name is in the eighth or ninth letter of the layer
name. For a series of similarly named layers, the layer box
in the toolbar indicates the first similar layer name.
For example, if layer PIPE-OBJM is the selected layer, the
box displays PIPE-OBJH (another valid layer name) but
PIPE-OBJM is indeed the current layer.
*66. In Paperspace, freezing and thawing layers at certain stages
of the drawing will result in a complete lock-up of the
system. The following script demonstrates the problem in a
new drawing.
----------- Start here
TILEMODE 0
LAYER NEW X
FREEZE X
MAKE Y
LINE
0,0
1,1
2,2
LAYER SET 0
FREEZE Y
THAW X
REGENALL
------------ End here
After the REGENALL, the system is locked tight. Currently,
the only known workaround is to have save the drawing after
doing the freeze/thaw combination, then use the OPEN command
to re-start the drawing. Any command that forces a regen
after the freeze/thaw could trigger this lockup. Fixed in
R12c3.
*67. If you create an ATTDEF using (entmake) calls, the attribute
prompts get converted to upper case. The workaround is to
immediately follow the (entmake) with an (entmod) to set the
prompts back to the original value you specified. Fixed in
R12c3.
68. When plotting from Paperspace, sometimes if you change the
zoom ratio within model space relatively recently prior to
plotting, the plotted drawing will often be of an earlier
zoom ratio view than what is displayed the screen. The paper
space drawing is of the correct size, only the zoomed or
panned view in the viewport into model space is incorrect.
The workaround is to save the drawing, open it back up, and
then replot. The status of this bug is unknown in R12c3.
*69. There are some errors in "DDMODIFY.LSP". On line 309,
"WIDTH" should be changed to "ROTATION ANGLE". On line 316,
"WIDTH" should be changed to "HEIGHT". These two changes
are only for the comments, the lisp data is correct. On
line 371, if the selected entity is an "ATTDEF" and text
justification is modified, the lisp routine does not work.
For TEXT, vertical text justification is set by group code
73 which is what DDMODIFY.LSP changes for both TEXT and
ATTDEF. However, for ATTDEF's group code 74 changes the
vertical text justification, not 73. Fixed in R12c3.
*70. Using (ssget "x") in an MNL file changes the value of the
MENUNAME system variable. To see this behavior copy
ACAD.MNU to TEST.MNU and create TEST.MNL containing only the
line:
(ssget "X" '((8 . "0")))
Load the TEST menu. If the (ssget) returned a selection set
the MENUNAME is "TSSn" where n is the number of the
selection set. If (ssget) returned nil the MENUNAME is
"_X". There is no known workaround. Fixed in R12c3.
71. In the FILTER dialogue, double clicking on an item in one of
the "Select..." subdialogues doesn't work. AutoCAD puts the
dialogue away, but the item isn't selected. To reproduce
the problem, load a drawing containing several layers and
linetypes. Start FILTER and select Layer as the filter
criterion. Click on "Select..." and when the layer list
comes up, double click on a layer name. AutoCAD returns to
the FILTER dialogue, but doesn't copy the layer name to the
X: text box. Ditto with using Linetype as a filter
criterion.
*72. In the Text Location subdialogue of DDIM, two of the choices
in the Alignment drop-down list are reversed. "Align When
Inside Only" turns DIMTIH on and DIMTOH off, as the manual
states, but the effect of these settings is to keep text
horizontal when it's inside the extension lines, and to
align it when the text is outside (exactly the opposite of
what the label and manual say).
Similarly, "Align When Outside Only" turns DIMTIH off and
DIMTOH on, which keeps text horizontal when it's outside the
extension lines, and aligns it when the text is inside.
Fixed in R12c3.
73. Undo doesn't work quite right with DDIM. To reproduce the
problem:
1) Start DDIM and save the current dimvars to a style
name, say STANDARD.
2) Draw a dimension (optional).
3) Start DDIM again and make any dimvar changes using one
of the Dimension Variable subdialogues. Close the DDIM
dialogue.
4) AutoCAD updates the dimension style. Now type U to
undo. AutoCAD (correctly) undoes the change to the
dimension style.
5) Start DDIM once more and note that the current style is
*UNNAMED, rather than STANDARD.
*74. The new "F", "CP", and "WP" selection methods do not honor
the setting of Orthomode. Fixed in R12c3.